Platform Explorer / Nuxeo Platform LTS 2019 10.10

Component org.nuxeo.ecm.core.api.pathsegment.PathSegmentService

In bundle org.nuxeo.ecm.core.api

Documentation

Component defining the implementation to use to compute the path segment for a new DocumentModel.

Resolution Order

117
The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.

Start Order

839
The start order represents the order in which this component has been started by the Nuxeo Runtime framework.
This number is interesting to tweak if your Java component interacts with other components, and needs to be started before or after another one.
It can be changed by implementing the method "Component#getApplicationStartedOrder()" on your Java component: components are sorted according to this reference value, in increasing order.
The default value is 1000, and the repository initialization uses number 100. Negative values can also be used.

Implementation

Class: org.nuxeo.ecm.core.api.pathsegment.PathSegmentComponent

Services

Extension Points

XML Source

<?xml version="1.0"?>
<component name="org.nuxeo.ecm.core.api.pathsegment.PathSegmentService">

  <implementation
    class="org.nuxeo.ecm.core.api.pathsegment.PathSegmentComponent" />
  <documentation>
    Component defining the implementation to use to compute the path
    segment for a new DocumentModel.
  </documentation>

  <service>
    <provide interface="org.nuxeo.ecm.core.api.pathsegment.PathSegmentService" />
  </service>

  <extension-point name="pathSegmentService">
    <documentation>
      Extension point defining the implementation for the computation of
      the path segment for new a DocumentModel. Example:

      <code>
        <service class="some-class" />
      </code>

      The provided class must implement org.nuxeo.ecm.core.api.pathsegment.PathSegmentService

      The default implementation is org.nuxeo.ecm.core.api.pathsegment.PathSegmentServiceDefault
      You can contribute org.nuxeo.ecm.core.api.pathsegment.PathSegmentServiceCompat
      to get pre-Nuxeo 5.4 behavior.
    </documentation>

    <object
      class="org.nuxeo.ecm.core.api.pathsegment.PathSegmentServiceDescriptor" />

  </extension-point>

</component>